Ingress Operator: Add optional e2e-gcp-operator job #15823
Conversation
openshift-ci-robot
added
the
approved
|
/lgtm |
Adds an optional, non-blocking e2e-gcp-operator job to exercise GCP specific operator-controller load balancer functionality. This commit is in support of https://issues.redhat.com/browse/NE-519.
sgreene570
force-pushed
the
ingress-operator-informing-gcp
branch
from
bec22fd to
417885a
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah, sgreene570 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@sgreene570: Updated the following 3 configmaps:
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Adds an optional, non-blocking e2e-azure-operator job to exercise the Ingress Operator's e2e test suite on Azure clusters. The Ingress Operator has a similair optional job for GCP (See openshift#15823), and a mandatory job for AWS. A PR against the Ingress Operator's master branch should have the ability to run against AWS, GCP, or Azure, since the operator has platform specific code for all of those platforms.
5 participants
Adds an optional, non-blocking e2e-gcp-operator job
to exercise GCP specific operator-controller load balancer
functionality.
This commit is in support of https://issues.redhat.com/browse/NE-519.
This job will be triggered by
/test e2e-gcp-operatorand will run the ingress-operator's e2e tests on a GCP IPI cluster. This will be useful to test different configurations for Load Balancer services on GCP (currently the operator's e2e tests are only run on AWS).